Skip to content

fix(agent): preserve millisecond provenance and session timestamps - #285

Merged
geekgonecrazy merged 2 commits into
feat/semweb-knowledge-graphfrom
fix/provenance-seconds-and-milliseconds
Oct 26, 2026
Merged

geekgonecrazy merged 2 commits into
feat/semweb-knowledge-graphfrom
fix/provenance-seconds-and-milliseconds

Conversation

@graywolf336

@graywolf336 graywolf336 commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Use milliseconds for new agent, provenance, and session timestamps; preserve subsecond durations and RPC precision.
  • Keep historical seconds readable and correctly ordered without rewriting payloads or hashes.
  • No KG upgrade, migration, or reindex required.

Validation

  • Core, agent, and RPC unit suites; targeted triage and CLI integration suites passed.
  • All 9 KG-projection tests and 3 end-to-end timestamp consistency regressions passed.

Accept second and millisecond epochs at the session-date formatting boundary. Normalize the old projector's expanded-year created_at strings only in returned session-ledger KG read models, including read-only queries.

Keep KG_GENERATION at 2. Do not require a migration, reindex, or writable open; leave timestamp producers, ordering, RPC payloads, provenance bytes, and session-manifest heads unchanged.

Add regressions using DDSB7T6MPKZB's 1792920379589 timestamp. Verify correct dates and millisecond precision, unchanged valid dates and unrelated nodes, and unchanged cached KG bytes and generation after read-only queries. Validation: 3683 core library tests and all 9 KG-projection integration tests pass.
Use millisecond epochs for new goal, reasoning, response, graph, request-metadata, turn-envelope, and session lifecycle writes. Preserve subsecond turn durations and keep explicit timestamp_millis graph construction separate from raw historical imports.

Share compatibility decoding and chronological comparisons across graph/session readers, trace export, triage, and CLI listings. Convert to protobuf seconds plus nanoseconds without losing milliseconds. Historical payloads remain byte-for-byte intact; causal links still take precedence over clocks. No KG generation bump, migration, or reindex is required.

Cover same-second actions through journal replay, graph preparation, session storage and KG projection; legacy seconds, mixed-unit ordering, clock skew, raw-byte preservation, fallback callbacks, envelope durations and RPC precision. Core, agent, RPC, KG-projection, triage and targeted CLI suites pass; final accumulator and consistency regressions also pass.
@graywolf336 graywolf336 changed the title fix(kg): render second and millisecond turn timestamps without upgrades fix(agent): preserve millisecond provenance and session timestamps Oct 26, 2026
@graywolf336
graywolf336 added this pull request to stack #287 October 26, 2026 11:22
@geekgonecrazy
geekgonecrazy merged commit 7d1813b into dev Oct 26, 2026
8 checks passed
@geekgonecrazy
geekgonecrazy deleted the fix/provenance-seconds-and-milliseconds branch October 26, 2026 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants